Skip to content

Add YugabyteDB as a Vector Store #19572

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Add YugabyteDB as a Vector Store #19572

wants to merge 2 commits into from
+6,428 −0

Conversation

@Sfurti-yb
Copy link
Contributor

@Sfurti-yb Sfurti-yb commented Jul 31, 2025

Description

Hi, I am reaching out on behalf of YugabyteDB,a high-performance, PostgreSQL-compatible distributed database built for global, internet-scale applications.

This contribution adds support for YugabyteDB as a vector store in LlamaIndex. The implementation is based on the existing PostgreSQL vector store, with modifications and enhancements specific to YugabyteDB’s architecture.

We’d appreciate it if you could review the changes and guide us on the next steps to have YugabyteDB officially listed as a supported vector store in LlamaIndex—similar to the Postgres example.

Looking forward to your feedback!

Fixes # (issue)

New Package?

Did I fill in the tool.llamahub section in the pyproject.toml and provide a detailed README.md for my new integration or package?

  • Yes
  • No

Version Bump?

Did I bump the version in the pyproject.toml file of the package I am updating? (Except for the llama-index-core package)

  • Yes
  • No

Type of Change

  • New feature (non-breaking change which adds functionality)
  • This change requires a documentation update

How Has This Been Tested?

Your pull-request will likely not be merged unless it is covered by some form of impactful unit testing.

  • I added new unit tests to cover this change

Suggested Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added Google Colab support for the newly added notebooks.
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • I ran uv run make format; uv run make lint to appease the lint gods

@dosubot dosubot bot added the size:XXL This PR changes 1000+ lines, ignoring generated files. label Jul 31, 2025
@Sfurti-yb
Copy link
Contributor Author

Sfurti-yb commented Aug 12, 2025

@logan-markewich Extending the PostgresVectorStore currently introduces psycopg2-binary as a transitive dependency. This creates a conflict with psycopg2-yugabytedb, our smart driver, which provides features such as load balancing to better leverage YugabyteDB’s distributed architecture.

Is there a way to inherit PGVectorStore without bringing in psycopg2-binary as a transitive dependency?

If this is not feasible, we propose proceeding with the current implementation without inheriting PGVectorStore. However, if it is important for your use case that we directly inherit the PGVectorStore code, we can make the necessary changes—though this would require removing certain smart driver features like load balancing.

Please let us know your preference so we can align accordingly.

@Sfurti-yb
Copy link
Contributor Author

Sfurti-yb commented Aug 19, 2025

@logan-markewich Gentle reminder here. Please let us know if there is something on our end that needs to be done. Thanks

@Sfurti-yb
Copy link
Contributor Author

Sfurti-yb commented Aug 27, 2025

@logan-markewich Gentle reminder to take a look at the PR. Thanks.

@Sfurti-yb Sfurti-yb force-pushed the vector-store-yugabytedb branch from 3b3f240 to a49e422 Compare September 3, 2025 08:03
@Sfurti-yb
Copy link
Contributor Author

Sfurti-yb commented Sep 8, 2025

@AstraBert Could you also take a look at this PR. Thanks.

@github-actions
Copy link
Contributor

github-actions bot commented Oct 29, 2025

This PR is stale because it has been open 50 days with no activity. Remove stale label or comment or this will be closed in 10 days.

@github-actions github-actions bot added the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Oct 29, 2025
@ashetkar
Copy link

ashetkar commented Oct 29, 2025

Any update on this PR @logan-markewich ?

@github-actions github-actions bot removed the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Oct 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@logan-markewich logan-markewich logan-markewich left review comments

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

size:XXL This PR changes 1000+ lines, ignoring generated files.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@Sfurti-yb @ashetkar @logan-markewich